mapping network drives, 2008 Terminal server "a device attached to the system is not functioning"
Hello everyone.. I have just setup a new 2008 Remote Desktop server in a a 2003 Domain. I am running into a strange situation where I am having trouble mapping Remote Desktop user network drives to a share located on a 2003 Domain controller. Sometimes I can create a drive mapping by using <servername>sharename, and sometimes I cannot. Then if I try <IP address>sharename it might work. And then another time it will not. I have tried creating desktop shortcuts to network shares. They may work for awhile (1/2 day or so) but then they disconnect. So it seems to be time/inactivity dependent? I am getting an error "a device attached to the system is not functioning". I have done some searching, and others have enabled the Routing and Remote Access service. I did this but it hasn't seemed to help. I am able to ping the 2003 server where the shares are located, by both name and IP address. I can see the 2003 shares from the 2008 server when I browse the network. The computers doing the Remote Desktop connections are Vista and Windows 7 pcs. There seem to be quite a few persons having an issue similar to this, from my network searches. I am continuing to test and monitor the problem, but would appreciate any advice from others on what to do to get this to work reliably. Please post back if you require further info. Thank you!
March 15th, 2011 9:58pm

Hello, sounds for me like DNS, please post an unedited ipconfig /all from the DC/DNS server the Remote desktop server and a problem client.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 6:25am

Meinolf: Thanks for the reply. Ipconfig /all from Domain Controller-2003 Server-server with the shares: Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : pmtsbs Primary Dns Suffix . . . . . . . : PMT.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : PMT.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : BCM5703 Gigabit Ethernet Physical Address. . . . . . . . . : 00-0B-CD-25-0F-51 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 10.252.96.130 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.252.96.254 DNS Servers . . . . . . . . . . . : 10.252.96.130 Primary WINS Server . . . . . . . : 10.252.96.130 C:\Documents and Settings\Administrator> Ipconfig /all from Remote Desktop Server: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\lindsaytech>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : PMTServer2008 Primary Dns Suffix . . . . . . . : PMT.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : PMT.local Ethernet adapter Local Area Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #2 Physical Address. . . . . . . . . : 84-2B-2B-63-00-6F DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) Physical Address. . . . . . . . . : 84-2B-2B-63-00-6D DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.252.96.3(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.252.96.254 DNS Servers . . . . . . . . . . . : 10.252.96.130 Primary WINS Server . . . . . . . : 10.252.96.130 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{58C12B80-1FE7-480F-8B85-93B68ECEFA64}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 12: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter isatap.{FB315933-9AF1-4BED-8669-38D3D56833EC}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\lindsaytech> Ipconfig /all from a client running a RD session: Microsoft Windows [Version 6.0.6002] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\user>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : HP-Pavillion Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Wireless LAN adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Con nection Physical Address. . . . . . . . . : 00-13-02-AE-0C-4C DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::54a2:e649:583:dd34%11(Preferred) IPv4 Address. . . . . . . . . . . : 10.252.96.177(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Thursday, March 10, 2011 4:23:39 PM Lease Expires . . . . . . . . . . : Thursday, March 17, 2011 4:23:38 AM Default Gateway . . . . . . . . . : 10.252.96.254 DHCP Server . . . . . . . . . . . : 10.252.96.254 DHCPv6 IAID . . . . . . . . . . . : 184554242 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-8B-2E-C7-00-16-D4-3A-9D-7A DNS Servers . . . . . . . . . . . : 10.252.96.130 66.133.170.2 Primary WINS Server . . . . . . . : 10.252.96.130 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection Physical Address. . . . . . . . . : 00-16-D4-3A-9D-7A DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 6: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{057586D5-CF70-4563-A21A-F3B472391 CDE} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 7: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{1E8C93D3-7888-4490-BB43-46DEE1AD6 D31} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 02-00-54-55-4E-01 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 17: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{057586D5-CF70-4563-A21A-F3B472391 CDE} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 18: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{057586D5-CF70-4563-A21A-F3B472391 CDE} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 19: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{057586D5-CF70-4563-A21A-F3B472391 CDE} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 20: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : isatap.{057586D5-CF70-4563-A21A-F3B472391 CDE} Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes C:\Users\user>
March 16th, 2011 9:47am

Meinolf: Thanks for the reply.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 9:48am

Hello, on PMTServer2008 i would disable RRAS functionality iof you don't use it. HP-Pavillion uses a NOT domain DNS server on the NIC which is the problem source for the sometimes working and sometimes not working connection. Please remove the 66.133.170.2 from the NIC and configure it as Forwarder on the DNS server properties in the DNS management console. I assume that is the ISPs DNS server as i can ping it via the internet. After the change run ipconfig /flushdns on the workstation and reboot.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
March 16th, 2011 10:23am

Meinolf: Thank you for the reply. Your help is appreciated! If I may clarify some things about the problem I am having: 1) There is a 2003 server/domain controller that has shared folders on it. There is a 2008 server running Remote Desktop Services. Both servers are on the same LAN. The 2008 server is a member of the 2003 server's domain. 2) Remote users connect to the 2008 server over the internet, to run a Remote Desktop Session. 3) Here is the problem: from within the Terminal Server session, running on the 2008 server, mapped drives to the 2003 server fail with the error I mention in my original post. Again: it is a drive mapped INSIDE the TS session, not a drive being mapped to the outside workstation running the TS session, that is having the problem. You advise changing settings on the HP-Pavillion. However this computer is only a TS client running a TS session on the 2008 server. The only communication between the HP Pavillion and the 2008 Terminal Server is keystrokes and screen shots. Please correct me if I am wrong: but it seems to me the issue is something between the 2008 Terminal Server, and the 2003 Server where the network shares are located (?) I can be sitting directly in front of the 2008 Terminal Server/Remote Desktop server and try to map a drive to the 2003 server, and still have the same problem as originally posted i.e. "device not functioning". Again--I do want to mention I appreciate your help.
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 11:12am

Meinolf: Thank you for the reply. Your help is appreciated! If I may clarify some things about the problem I am having: 1) There is a 2003 server/domain controller that has shared folders on it. There is a 2008 server running Remote Desktop Services. Both servers are on the same LAN. The 2008 server is a member of the 2003 server's domain. 2) Remote users connect to the 2008 server over the internet, to run a Remote Desktop Session. 3) Here is the problem: from within the Terminal Server session, running on the 2008 server, mapped drives to the 2003 server fail with the error I mention in my original post. Again: it is a drive mapped INSIDE the TS session, not a drive being mapped to the outside workstation running the TS session, that is having the problem. You advise changing settings on the HP-Pavillion. However this computer is only a TS client running a TS session on the 2008 server. The only communication between the HP Pavillion and the 2008 Terminal Server is keystrokes and screen shots. Please correct me if I am wrong: but it seems to me the issue is something between the 2008 Terminal Server, and the 2003 Server where the network shares are located (?) I can be sitting directly in front of the 2008 Terminal Server/Remote Desktop server and try to map a drive to the 2003 server, and still have the same problem as originally posted i.e. "device not functioning". Again--I do want to mention I appreciate your help. I have to ask Zooey to edit their proprietary domain information to remove it so that it may not be used by unethical bodies. Rename your domain controller to DC1, rename your RD Server to RDS1. This is to help protect you from undesired attention to your domain. Anyone with a mind to run a google query can find this easily and use it against you. I have to ask, how was the 2008 server setup as far as 2008 Server Services? I want to make sure I'm understanding your infrastructure completely before saying whether or not why something may not work properly. I might have a discrepency with the configuration but... none-the-less I'll try my best to help as well. DNS Settings What is the main reason for using WINS? How is your DNS Setup? My other question, have you run some packet sniffer on the DC or RDS to determine why the connections are being denied or where the information regarding the "bad" device is coming from? I would definately check some event logs on the DC to make sure the disks aren't leaning towards a failing state as well. Server 2008 has a little bit more definitive hardcode for detecting hard drive failures waiting to happen. I just helped a gentleman the other day on here resolve a Western Digital issue because Windows informed him the Hard disk is about to fail. The outcome was he able to RMA and backup the data on the disk before the failure actually occured. Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Product Specialist Microsoft Certified Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.
March 16th, 2011 12:18pm

Thanks for the reply. The reason we use WINS: there is a legacy application that requires it. DNS setup: local computers are set to use the DC as their DNS server. The DNS on the DC is setup strictly as a forwarder. Haven't run any packet sniffer as of yet. Checked the server logs on the DC: cannot see any errors regarding hard disks. I do want to mention that everything seems to be working ok today. It may be that for some reason the problem has resolved itself (?)
Free Windows Admin Tool Kit Click here and download it now
March 16th, 2011 1:57pm

Hello, thanks for clarifying again, got it now. What kind of device is connected to the DC? Is that a USB drive or SAN/NAS system? As DNS domain internal is correct it should be hardware related and i would contact the vendor about. For the workstation, if you connect it that way direct to the domain subnet you can/will run into problems with the external DNS server on the NIC.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
March 16th, 2011 2:53pm

Thanks for the reply. The reason we use WINS: there is a legacy application that requires it. DNS setup: local computers are set to use the DC as their DNS server. The DNS on the DC is setup strictly as a forwarder. Haven't run any packet sniffer as of yet. Checked the server logs on the DC: cannot see any errors regarding hard disks. I do want to mention that everything seems to be working ok today. It may be that for some reason the problem has resolved itself (?) Zooey, thanks for responding. Did you run hard drive diagnostics or just view Event Viewer? Event Viewer will not show those errors typically for hard drives detected to fail prematurely. If you see it, it would typically show in device manager for devices behaving badly. Hard Drive diagnostics would be most effective. You can download them from support pages of the drive manufacturers. Also, some storage controllers like Intel Matrix Storage Manager will notify suspected disks getting close to failure. If that's not the case, no worries. Then you might want to concern yourself with the mapped drive driver. I would rather be safe then sorry! Make sure you got good and tested backups! As far as your clients mapped drive or dns issue to your domain controller/file server, in the future, you could always run ipconfig /flushdns on your RDS server to see if clearing some stale DNS information will help resolve your issue. I'm glad everything is working ok for you. Sometimes a good reboot never hurts either... No one said Server 2008 was bulletproof from Memory Leaks.... =) Best Regards Zooey,Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Product Specialist Microsoft Certified Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.
Free Windows Admin Tool Kit Click here and download it now
March 18th, 2011 12:40pm

Hi Zooey, Whether your problem has been solved. Looking forward to your feedback.Technology changes life
March 21st, 2011 6:59am

Hi everyone. Sorry it took me a while to get back. But wanted to let everyone know that I have NOT been experiencing the problem---ever since I did a reboot of the server four days ago. So---maybe it was something with DNS, or maybe just one of those issues that required a server reboot. So---for the time being I think we mark this "case resolved". Always a little worrisome when something like this happens with nothing obvious causing it. But then again it may never recur. I am shortly going to be upgrading the 2003 Domain Controller to Server 2008, which can only help for things like this. I do want to thank everyone for the help/advice. It is appreciated.
Free Windows Admin Tool Kit Click here and download it now
March 21st, 2011 5:30pm

Same issue here. 1. DC - 192.168.0.222 2. TS - 192.168.0.250 3. Srv01 - 192.168.0.5 All users work on the terminal server (TS) that is part of the DC, when user log in (Logon script), a network drive is mapped, the Folder mapped is on Srv01. Here is a part of the script... -------------------------------------------------------------------- Option Explicit Dim objNetwork Dim objWshShell Dim strRemotePath, strLocalPath, strUserName Dim strRegPath, strRegKey ' Dim strLogonPath Set objNetwork = WScript.CreateObject("WScript.Network") Set objWshShell = CreateObject("WScript.Shell") strRemotePath = "\\srv01\Saved" strLocalPath = "\\localhost\Profiles$\" strUserName = objNetwork.UserName .... --------------------------------------------------------------------- Now about the problem, sometimes (it happens already to frequently) when users log in the network drive is not mapping, when I try to go directly to the map \\srv01\Saved I get the "a device attached to the system is not functioning" error, sometimes there is another error, something like "map cannot be found", cannot understand why this is happening, there are no errors in EventViewer regarding this problem, only EventID 602 (The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-1178597828-3712073033-1381665325-1135\Printers\Connections\,,HP LaserJet 1020. This can occur if the key name or values are malformed or missing.) detected... To solve this issue at that moment I'm changing the computer name (srv01) to IP, strRemotePath = "\\192.168.0.2\Saved" and this solution works for a few days after that I get the same error after that nobody can work and I have to reboot the Server. One thing srv01 is not part of the domain... Here are the ipconfig output for all servers: DC-srv: ----------------------------------------------------------------------- C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : dc-srv Primary Dns Suffix . . . . . . . : va.net Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : va.net Ethernet adapter LAN: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Citrix XenServer PV Ethernet Adapter Physical Address. . . . . . . . . : A6-B7-6A-A6-F1-6C DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.222 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 127.0.0.1 192.168.0.1 C:\Documents and Settings\Administrator> ----------------------------------------------------------------------- TS-srv: D:\Profiles\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : TS-SRV Primary Dns Suffix . . . . . . . : va.net Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : va.net Ethernet adapter LAN: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Citrix XenServer PV Ethernet Adapter Physical Address. . . . . . . . . : D6-1F-34-60-62-FC DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::c453:e19f:790f:2dfd%14(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.250(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 290108353 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-28-29-23-4B-B3-C1-54-8E-20 DNS Servers . . . . . . . . . . . : 192.168.0.222 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{98678694-725D-4A29-A542-381E3291F9DF}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes D:\Profiles\Administrator> ----------------------------------------------------------------------- srv01: C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : srv01 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC Physical Address. . . . . . . . . : 00-50-FC-CE-2C-28 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 C:\Documents and Settings\Administrator> ----------------------------------------------------------------------- What causes this issue ? And how to solve it ? Thank you in advance....
June 2nd, 2011 7:23am

Same issue here. 1. DC (WinSrv 2003) - 192.168.0.222 2. TS (WinSrv 2008) - 192.168.0.250 3. Srv01 (WinSrv 2003) - 192.168.0.5 All users work on the terminal server (TS) that is part of the DC, when user log in (Logon script), a network drive is mapped, the Folder mapped is on Srv01. Here is a part of the script... -------------------------------------------------------------------- Option Explicit Dim objNetwork Dim objWshShell Dim strRemotePath, strLocalPath, strUserName Dim strRegPath, strRegKey ' Dim strLogonPath Set objNetwork = WScript.CreateObject("WScript.Network") Set objWshShell = CreateObject("WScript.Shell") strRemotePath = "\\srv01\Saved" strLocalPath = "\\localhost\Profiles$\" strUserName = objNetwork.UserName .... --------------------------------------------------------------------- Now about the problem, sometimes (it happens already to frequently) when users log in the network drive is not mapping, when I try to go directly to the map \\srv01\Saved I get the "a device attached to the system is not functioning" error, sometimes there is another error, something like "map cannot be found", cannot understand why this is happening, there are no errors in EventViewer regarding this problem, only EventID 602 (The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-1178597828-3712073033-1381665325-1135\Printers\Connections\,,HP LaserJet 1020. This can occur if the key name or values are malformed or missing.) detected... To solve this issue at that moment I'm changing the computer name (srv01) to IP, strRemotePath = "\\192.168.0.2\Saved" and this solution works for a few days after that I get the same error after that nobody can work and I have to reboot the Server. One thing srv01 is not part of the domain... Here are the ipconfig output for all servers: DC-srv: ----------------------------------------------------------------------- C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : dc-srv Primary Dns Suffix . . . . . . . : va.net Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : va.net Ethernet adapter LAN: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Citrix XenServer PV Ethernet Adapter Physical Address. . . . . . . . . : A6-B7-6A-A6-F1-6C DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.222 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 127.0.0.1 192.168.0.1 C:\Documents and Settings\Administrator> ----------------------------------------------------------------------- TS-srv: D:\Profiles\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : TS-SRV Primary Dns Suffix . . . . . . . : va.net Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : va.net Ethernet adapter LAN: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Citrix XenServer PV Ethernet Adapter Physical Address. . . . . . . . . : D6-1F-34-60-62-FC DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::c453:e19f:790f:2dfd%14(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.250(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 290108353 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-28-29-23-4B-B3-C1-54-8E-20 DNS Servers . . . . . . . . . . . : 192.168.0.222 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{98678694-725D-4A29-A542-381E3291F9DF}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 11: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes D:\Profiles\Administrator> ----------------------------------------------------------------------- srv01: C:\Documents and Settings\Administrator>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : srv01 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8139/810x Family Fast Ethernet NIC Physical Address. . . . . . . . . : 00-50-FC-CE-2C-28 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.1 DNS Servers . . . . . . . . . . . : 192.168.0.1 C:\Documents and Settings\Administrator> ----------------------------------------------------------------------- What causes this issue ? And how to solve it ? Thank you in advance. ...
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2011 7:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics